OneKey Trace Process

The monitor stream manages tracing the submitted DCR's to Onekey as described in the section Monitor Stream under Real Time Streaming Configuration Details & Near real time profile insert/update following a Onekey VR response through DCR process.

OneKey Trace process can process the OneKey Trace response when an event of type “ONEKEY_RESPONSE” is received by the enrich stream. The Onekey response which is part of the event payload is analyzed in this process and based on the ‘requestStatus’ value, the DCR is marked approved or rejected or it may stay in PENDING state.

Non ok attributes from external sources can be appended to OK reltio profile.

See the Event Payload data example for a DCR below:

"eventPayload":

The OneKey Trace process analyzes the event payload to see what the current status of the DCR is in Onekey. If the DCR has been approved in OneKey then the Trace process can mark the DCR as approved in Relito or if the DCR has been rejected in OneKey then it can mark the DCR as rejected in Reltio.

Below is the list of OneKey Trace Status vs Reltio DCR Approve/Reject in Onekey Trace process:

OneKey Response (requestStatus)

Next Workflow Step

VAS_FOUND

Approve

VAS_NOT_FOUND

Reject

VAS_FOUND_BUT_INVALID

Reject

VAS_INCOHERENT_REQUEST

Reject

VAS_DUPLICATE_REQUEST

Reject

The OneKey trace process can also update the database table ODP_CORE_STREAM.DCR_VALIDATION for OneKey response as shown in the below screenshot:

The OneKey Trace process can update the following columns in this database table:

STATUS

RESPONSE_SOURCE_EVENT_ID

RESPONSE_DT

RESPONSE_PAYLOAD

RESPONSE_IDS

RESPONSE_STATUS

RESPONSE_COMMENTS

SYS_UPDT_DT

Note:   

The table column STATUS is updated by all the processes – OneKey Submit, Monitor and OneKey Trace.

Once the DCR is approved or rejected and OneKey trace is complete, the externalInfo of the DCR is also updated to reflect this update to the DCR, see example below:

  1. Rejected in OneKey

    Copy 
    "externalInfo": {
        "User": "UI",
        "OK-Activity-EidSource": "",
        "DCR_Type": "HCP",
        "DCRStatus": "Pending",
        "OK_OvUri_Status": "Rejected",
        "OK-Response-Comment": "REJECTED:[individual.preferredLanguageEID: DICO.DATABASE-STRING-maxChars ]",
        "System": "RELTIO",
        "OK-Trace-Run-Dt": "2021-12-01T19:46:37.191",
        "OK-Individual-EidSource": "",
        "RequestDate": "2021-11-01T16:17:57",
        "STATUS": "Reject",
        "OK-Workplace-EidSource": "",
        "OK-Address-EidSource": "",
        "OKSTATUS": "ACCEPT",
        "OK-Last-Update-Dt": "2021-11-01T16:25:02Z",
        "OK-Address-EidValidated": "",
        "CreatedBy": "UI",
        "OKREQUESTID": "OkResponse(response=OkResponse.Response(success=true, status=SUCCESS, errors=null, validationClientRequestId=3FHKwRZD, resultSize=1, results=null), status=null, total=0, offset=null, size=0, data=null)",
        "IND_ID": "entities/1OXGCKbX",
        "OK-Workplace-EidValidated": "",
        "OK-Trace-status": "VAS_INCOHERENT_REQUEST",
        "Vendor": "OK",
        "DCR_InsertUpdate": "U",
        "RequestProcess": "U",
        "stage": "Reject",
        "OK-Activity-EidValidated": "",
        "OK-Individual-EidValidated": "",
        "Country": "CA",
        "OK-Client-Request-Dt": "2021-11-01T16:17:57Z",
        "RequestClientID": "3FHKwRZD",
        "OKSENTDATE": "2021-11-01T16:20:07",
        "OK-Response-Dt": "2021-11-01T16:24:37Z"
    }

  2. Approved in OneKey

    Copy 
    "externalInfo": {
        "WKP_ID": "entities/163AzuGo",
        "User": "UI",
        "OK-Activity-EidSource": "",
        "DCR_Type": "HCO",
        "DCRStatus": "Pending",
        "OK_OvUri_Status": "Accepted",
        "OK-Response-Comment": "",
        "System": "RELTIO",
        "OK-Trace-Run-Dt": "2021-11-15T21:02:54.621",
        "OK-Individual-EidSource": "",
        "RequestDate": "2021-11-01T16:22:12",
        "STATUS": "VAS_FOUND",
        "OK-Workplace-EidSource": "",
        "OK-Address-EidSource": "",
        "OKSTATUS": "ACCEPT",
        "OK-Last-Update-Dt": "2021-11-12T09:30:23Z",
        "OK-Address-EidValidated": "WCA00000005630",
        "CreatedBy": "UI",
        "OKREQUESTID": "OkResponse(response=OkResponse.Response(success=true, status=SUCCESS, errors=null, validationClientRequestId=3wrHNcse, resultSize=1, results=null), status=null, total=0, offset=null, size=0, data=null)",
        "OK-Workplace-EidValidated": "WCAH00172153",
        "OK-Trace-status": "VAS_FOUND",
        "Vendor": "OK",
        "DCR_InsertUpdate": "U",
        "RequestProcess": "U",
        "stage": "Success",
        "OK-Activity-EidValidated": "",
        "OK-Individual-EidValidated": "",
        "OvUri": "",
        "Country": "CA",
        "OK-Client-Request-Dt": "2021-11-01T16:22:12Z",
        "RequestClientID": "3wrHNcse",
        "OKSENTDATE": "2021-11-01T16:23:16",
        "OK-Response-Dt": "2021-11-12T09:27:23Z"
    }

    Note:   

    These attributes are added/appended to the DCRs externalInfo by the OneKey Submit as well as OneKey Trace processes.

Configuration Parameter waitForOkOvBeforeAccept

The configuration setting for parameter waitForOkOvBeforeAccept may be updated in the database table ODP_CORE_STREAM.DCR_STREAMING_CONFIGURATION under configuration dcr-global-config.

If the parameter waitForOkOvBeforeAccept is set as shown in the below screenshot then the DCR can only be approved in Reltio if the OvUri for the given entity type is found in Reltio else the DCR can still stay in open status in Reltio.

As noted earlier, the default setting for this parameter is NO.